✨Rollout options added to HelmChartProxy #452
Draft
+1,693
−169
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This is a rework of an earlier merge request #443 to add an initial rollout size within
HelmChartProxy.This change adds in a new optional field called
rollout, using which you can define an initial step size, optionally an increment size and a limit to how much the rollout step size can be increased to. These options can be defined individually for installs vs upgrade operations, allowing you to setup a different strategy for each kind of operation. Rollout quantities can be defined as an integer or a percentage of the total matched count of clusters. Below is an example showing the rollout option:A new status condition
HelmReleaseProxiesRolloutCompletedis added to denote rollout progress and is baked into the overallReadycondition set at the resource level.